Hi,
You start an HDD session for a story. The story already records whether the workflow is Full or Lightweight, and the session already knows where progress notes belong.
Your coding agent shouldn’t make you supply that context again.
I just published imdone CLI 0.96.0.
In an explicit HDD session, enabled progress notes now use the retained session story without asking you to select it again. When saved story metadata unambiguously identifies Full or Lightweight HDD, imdone uses that too.
Ordinary direct-agent and imdone ai sessions stay quiet.
That means less setup chatter—and a better chance that decisions and learning stay attached to the story your team will return to.
Also in this release:
Codex and Claude hooks keep working when an imdone plugin update replaces their original versioned cache.
Targeted pull and push operations for different stories can overlap without publishing each other’s changes.
Try one small experiment:
npm install -g imdone-cli
imdone hdd YOUR-STORY-KEY
Run one HDD session, then reply with two results:
How many times did the agent re-ask for the story or HDD mode?
Did any progress note target the wrong story?
Docs: https://imdone.io/docs/imdone-cli/
Jesse
0 comments